Skip to content

docs(widget/wordpress): align integration & overview with the shipped plugin - #451

Open
ketanyekale wants to merge 1 commit into
mainfrom
ketanyekale/eng-37952-docs-gap-wordpress-widget-rewrite-overview-integration
Open

docs(widget/wordpress): align integration & overview with the shipped plugin#451
ketanyekale wants to merge 1 commit into
mainfrom
ketanyekale/eng-37952-docs-gap-wordpress-widget-rewrite-overview-integration

Conversation

@ketanyekale

Copy link
Copy Markdown
Member

What & why

Addresses ENG-37952 (AgentBuddy DOCUMENTATION_GAP, ticket #45163, appears in both the Jul 15–22 and Jul 21–28 tabs). The WordPress widget docs described a plugin UI that doesn't match what ships, which led an AI agent to answer a support ticket incorrectly end-to-end.

Changes

integration.mdx

  • Removed the non-existent "CometChat UI Kit Builder" sidebar item, "Default User UID" field, and plugin-level "Display Mode" setting from Configure Plugin Settings.
  • Documented the real auth model: the widget is gated by WordPress's is_user_logged_in(), and the plugin auto-maps each logged-in WP user to a CometChat UID with a securely generated auth token (no fixed UID in the plugin).
  • Docked vs. embedded is driven by the shortcode docked attribute; reworked the "every page" step to use the shortcode instead of a Display Mode setting.
  • Added Anonymous & guest access guidance and a Customize the widget with CSS section (Widget Builder → Custom Code tab, --cometchat-* variables) with the correct dashboard nav path.

overview.mdx

  • Fixed button label "Get Embedded Code" → "Get Embed Code".
  • Added a short Customization pointer to the new CSS section.

⚠️ Reviewer verification needed (treated the L2/sheet findings as source of truth)

I don't have the shipped plugin source, so please confirm these before merge:

  1. Real plugin settings location/label — I replaced "CometChat UI Kit Builder in the sidebar" with a neutral "open the CometChat plugin settings." Please set the exact WP admin menu label.
  2. is_user_logged_in() gate + auto UID mapping + auto auth-token — stated per L2; confirm wording matches plugin behavior.
  3. Guest access recipe — described at a high level (WP-side guest sign-in); confirm the recommended approach.
  4. "Get Embed Code" label — the old "Get Embedded Code" string is still used in 12 other files (all other widget platforms + snippets/widget/overview.mdx + several ai-agents/* pages). If the real button is "Get Embed Code", those should be updated in a follow-up; I scoped this PR to the WordPress ticket only.
  5. --cometchat-* example values — the two variables shown are illustrative; confirm the canonical widget theming variables.

Fixes ENG-37952

🤖 Generated with Claude Code

Rewrite the WordPress widget docs to match the plugin's actual behavior
(per L2 findings captured in the AgentBuddy review):

- Remove the non-existent "CometChat UI Kit Builder" sidebar item,
  "Default User UID" field, and plugin-level "Display Mode" setting from
  the Configure Plugin Settings step.
- Document the real auth model: the widget is gated by is_user_logged_in()
  and auto-maps each logged-in WordPress user to a CometChat UID with a
  securely generated auth token.
- Drive docked/embedded display via the shortcode's `docked` attribute
  (not a Display Mode setting); rework the "every page" step accordingly.
- Add "Anonymous & guest access" guidance (WP-side guest sign-in).
- Add "Customize the widget with CSS" (Widget Builder Custom Code tab +
  --cometchat-* CSS variables) with the correct dashboard nav path, and a
  pointer from overview.
- Fix button label "Get Embedded Code" -> "Get Embed Code" in overview.

Fixes ENG-37952

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Aug 4, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cometchat 🟢 Ready View Preview Aug 4, 2026, 6:00 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant